home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
rbbs_pc
/
rbtch180.zip
/
RBATCH.DOC
< prev
next >
Wrap
Text File
|
1992-08-28
|
52KB
|
1,303 lines
------------------------------------
RBatch - RBBS-PC Batch Uploading
HS/Link, & BiModem
Interface
------------------------------------
RBatch Version 1.80
August 29, 1992
By: Dan Shore - SYSOP
THE SHORELINE BBS
(301-946-2771)
TABLE OF CONTENTS
-----------------
A. INTRODUCTION
1. What is RBatch .................................... 3
2. What it does ...................................... 3
B. INTERFACING RBATCH WITH RBBS-PC
1. The RBatch Configuration File ..................... 4
2. Line-by-line analysis of the configuration file ... 5
3. Additional notes on the configuration file ........ 12
4. The RBBS-PC Proto.Def Setup ....................... 13
5. Batch Files used in Proto.Def ..................... 14
6. The RBatch Command Line ........................... 15
7. SysOp Designed Batch Files ........................ 15
8. Batch File Passed Parameters ...................... 16
9. Calling other testers from the batch files ........ 16
10. Batch File Examples ............................... 16
11. Colorized Batch Files ............................. 17
12. Alternate Batch File Names ........................ 19
13. Flexibility in RBatch File Processing ............. 19
C. MISCELLANEOUS INFORMATION
1. Use of Recovery with Protocols and RBatch ......... 19
2. User Time-Outs and Dropped Carriers ............... 19
3. RBatch Error Logging .............................. 20
4. What Do The Included Merges Do .................... 21
5. Why Is RBatch An External Program ................. 21
6. Companion Program For RBatch ...................... 21
7. Warranty And Disclaimer ........................... 22
8. Registration ...................................... 22
9. Acknowledgments ................................... 23
10. Support ........................................... 24
-2-
A. INTRODUCTION:
A-1. What is RBatch?
---------------
RBatch is an upload interface utility for RBBS-PC Bulletin Board Systems.
RBatch enables RBBS-PC (versions 12.x-17.4) to receive and process BATCH
uploads. It is an EXTERNAL program (NO code modification is necessary)
that is called by RBBS after file transfers. It reads a standard, "true"
DSZ log file (XFER-?.DEF) generated by most of today's better file transfer
protocols, and reports the uploaded information to RBBS's system files
in ways that make the SysOp's job much easier and less time-consuming.
RBatch is fossil-aware, but does NOT require a fossil to run.
RBatch also is the interface for the new and extremely popular protocol,
HSLINK, by Sam Smith--and the BiModem bi-directional protocol.
A-2. What it does?
-------------
RBatch is called after file transfers are completed, and will:
- check each file uploaded to see if it is a DUPLICATE of
a file already on the BBS. This is accomplished by RBatch
checking the FFS (FIDX.DEF & FIDXT.DEF) and/or the SysOp
designated directories that are listed in the RBatch
configuration file.
- check uploaded file INTEGRITY with SysOp designed batch files.
Files may be scanned for viruses, unwanted uploads, files too
old, etc. Comments and logos may be stripped or added in these
BATCH FILES.
- ask the user for an upload CATEGORY (if security level allows),
and a DESCRIPTION of the file. Or, optionally, process
FILE_ID.DIZ, DESC.SDI or .DOZ files AUTOMATICALLY and post
the file descriptions in them to the FMS. No TYPING!
(See WHATISA.DOZ for details on RBatch's new and revolutionary
.DOZ File Descriptions Process).
- post all necessary information to the FMS directory, USERS,
& CALLERS files.
- Award time credits for the upload based on the user's security level.
***********************************************************************
* NOTE: RBatch is responsible for the logging and processing of ALL *
* uploaded files, while RBBS is responsible for ALL downloaded *
* files. *
***********************************************************************
-3-
B. INTERFACING RBATCH WITH RBBS:
Three things are crucial to the proper "marriage" between RBatch and
RBBS-PC:
1. The RBatch configuration file. (Which you must create.)
2. The RBBS PROTO.DEF file. (Which you must modify.)
3. The Batch Files that are in the Proto.Def. Example are
included, just change them to match your system.
B-1. The RBatch configuration file:
------------------------------
Here is the layout and description of each line in the RBatch
configuration file. (Note that the configuration file CANNOT
have comments like those in the example below!):
D:\Uploads;YES ### <-- 1 Path to upload directory;Pause Prompt
No;C:\Rbbs\Dorinfo[NODE].Def <-- 2 Create;Path to DORINFOx.DEF
ZIP;LZH;ARJ;ZOO;EXE <-- 3 Archive types to check for
5,50;10,100;15,150;20,200 <-- 4 Security level,credit parameters
C:\Rbbs\Master.Dir;NONE <-- 5 FMS;2nd place to write
BLANK <-- 6 Path to NON-FMS dirs
C:\Rbbs\Messages <-- 7 Path to RBBS MSG file
C:\Rbbs\Users <-- 8 Path to RBBS USERS file
C:\Rbbs\Caller[NODE] <-- 9 Path to RBBS CALLERS file
C:\Rbbs\Dir.Cat <-- 10 Path to RBBS directory categories
C:\Rbbs\Xfer-[NODE].Def <-- 11 Path to DSZ transfer log
SECRET NAME <-- 12 SYSOP'S secret name
5;C:\Rbbs\Upcat.Hlp <-- 13 SEC for cat.;Hlp file for upcat
FMS <-- 14 Using FMS or .DIR
UNC <-- 15 Default category code
ZIP <-- 16 Extension to convert to
YES <-- 17 Save files on timeouts/errors?
NO <-- 18 Using FOSSIL?
46 <-- 19 # characters in description line
5;NO <-- 20 # lines in FMS descriptions
YES;C:\Rbbs\Fidx.Def <-- 21 Use FIDX system?;location
C:\Rbbs\Dupelist.Lst <-- 22 Additional DIRs to look for dupes
DV <-- 23 Environment running
THE SHORELINE BBS <-- 24 BBS Name
00000000000000000000 <-- 25 Registration # (or all 0's)
YES;C:\Work;C:\Arc.Lst <-- 26 CHECK for DOZ?;WORK dir;archives
BATCH.BAT;BATCH1.BAT;BATCH2.BAT <-- 27 OPTIONAL PARAM naming BAT files
< ### = Denotes New Parameters for RBatch 1.80 >
This is the heart of the RBatch process. This text file tells RBatch
the name and location of all the files that it needs or uses on your
system. It sets security levels, upload credits, paths, duplication
checking methods, designates batch files to call scanning programs and
archive checkers, and much more.
-4-
This file may be created with your favorite editor, like QEdit or QDos
editor, and may be named anything you wish, or stored anywhere on the
system. All you need to do is tell RBatch the name and location of
its configuration file on the RBatch command line. THERE IS NO
DEFAULT FILENAME THAT RBATCH LOOKS FOR.
B-2. Line-by-line analysis of the RBatch configuration file:
-------------------------------------------------------
1. Path to Upload Directory;Pause Prompt
- This is the full path to your Upload Directory.
(Path/Dir - NO TRAILING BACKSLASH)
- 20 Second Pause Prompt - enter YES after semi-colon. If you
just have your path to the Upload Directory and NO SEMI-COLON
then the feature is DISABLED. The pause prompt stays for 20
seconds or until user hit ENTER Key.
Pause prompt looks like this: Press [ENTER] to continue: . . .
Dots will go back and forth until user hits enter or 20 Secs. passes
### (This is a new feature for 1.80)
2. Shall RBatch create a DORINFOx.DEF;Path/name of the DORINFOx.DEF file:
First parameter MUST be either YES or NO. If you are
running RBBS-17.4, you would specify "NO." (RBBS v.17.4
is the first version to create its own DORINFOx.DEF file
for DOORING protocols) for the first parameter, and the
location of the DORINFOx.DEF file for the second parameter.
All earlier versions of RBBS prior to 17.4 specify "YES"
and RBatch will create a "working" copy of the DEF file in
this specified location. (Note semicolon...)
If you examine this file when RBatch creates it,
you will notice that it does not have the "normal"
==== DORINFO information in it. Do not be concerned, I only ====
write the information I need to run RBatch.
NO = RBatch DOES NOT create ; path to RBBS's (17.4) own file
YES = RBatch DOES create ; where you want us to put it
3. Extensions to check for duplicates -- or NONE:
This parameter allows the SysOp to specify which
extensions to check when RBatch checks for duplicates
of uploaded files. If SysOp only wants the uploaded file
checked just input the word NONE here instead.
ARC;ZIP;LZH;ZOO
NOTE: ALL THE EXTENSIONS MUST BE SEPARATED BY A SEMI-COLON!!!
-5-
4. Security Level,Time CREDIT percentage given for UPLOADS (###):
Time credits may now be assigned by security level(s).
The format for the Time Credit line in the configuration file is:
SECURITY LEVEL1,PERCENTAGE1;SECURITY LEVEL2,PERCENTAGE2
Here is an example: 5,125;10,150;15,175;25,200
Users with security levels LESS THAN OR EQUAL TO 5
would get 125%,
Users with security levels between 6 and 10 would get 150%,
Users with security levels between 11 and 15 would get 175%,
Users with security levels between 16 and 25 would get 200%.
~(Note the way commas and semicolons are used on this line.)
You must have the HIGHEST value security level at the minimum
if just using one time credit percentage. In other words, if
the highest security level of a user on your BBS is 100, and you
want ALL your users to have 100% time credits, then your
configuration line would be:
100,100
Remember that RBatch checks to see if the user's security
level is LESS THAN OR EQUAL TO the security level(s) on this
line and then uses the associated percentage.
Note also, that if you use multiple security levels, this line
should read (left to right) from lowest security level to the
highest, just like the examples.
Currently you may define up to twenty security levels.
The amount of time credit received (based on the percentage) is
calculated as shown in these examples:
Ex. # 1 - File upload time = 5:00 Minutes
Time Credit% = 150% (7:30 Minutes)
5:00 + 7:30 = 12:30 of Time Credits
Ex. # 2 - File Upload Time = 5:00 Minutes
Time Credit% = 50% (2:30 Minutes)
5:00 + 2:30 = 7:30 of Time Credits
Ex. # 3 - File Upload Time = 5:00 Minutes
Time Credit% = 0%
5:00 + 0 = 5:00 of Time Credits
The User always gets the time back it took to upload the file,
plus the percentage that you assign in the configuration file.
-6-
5. Path/Name of primary FMS DIR file;Path/Name of secondary FMS DIR file:
This is the text directory where the uploaded filenames and their
descriptions are WRITTEN. If you wish to post this information
to more than one file, list the path/name of the second file AFTER
the Semi-Colon. If you do not wish to post to more than one file,
then you must enter "NONE" as the second parameter.
6. Path to the .DIRs - Enter the word "BLANK" if using FMS:
This is the path to where your .DIR's are. An example of
this is:
C:\FILES\
7. Path/Name to MESSAGES File:
8. Path/Name to USERS File:
9. Path/Name to CALLERS File:
10. Path/Name to DIR.CAT File:
11. Path/Name to XFER-?.DEF File:
Protocols ALWAYS write the Xfer-?.Def file in the CURRENT directory
when the protocol is invoked. Make sure that you have your
SET DSZLOG=XFER-?.DEF (? = Node #) in your AUTOEXEC.BAT or your
DESQVIEW startup window batch file. Do not use a path in
your SET DSZLOG statement.
For example, if you are in the RBBS directory when you execute
DSZ, the XFER-?.DEF file will reside in the RBBS Directory.
If you change to your upload directory when you invoke DSZ,
the XFER-?.DEF file will reside in your upload directory.
Note that RBatch will DELETE the XFER-?.DEF file, when there
are just uploads.
If you are doing bidirectional transfers, the XFER will have
to be located in the current directory as the user when doing
a transfer (the Main RBBS directory or the Node Directory).
RBatch will not delete the XFER due to RBBS needing to "see"
the XFER file to report a successful transfer.
12. SysOp's secret name (ALL CAPS):
Enter "BLANK" if you do not wish the USERS file to be updated
with file count information for SysOp file transfers.
-7-
13. Min Security Level to Categorize;Path/Name of UPCAT.HLP File:
The First Parameter is the MINIMUM security level a user must have
in order to categorize a file that he/she uploaded. If their level
is LOWER than this value, the uploaded file will have the default
category code for FMS (line #15), and in the .DIR system, will be
posted to the file listed on line #5 in this configuration file.
The Second Parameter is the path/filename of the UPCAT.HLP file.
< A useful feature for SYSOPS is that you do not have
to use the SAME UPCAT.HLP file you specify in RBBS's
CONFIG parameter #! The file you specify here may
display entirely different categories, or you may
create a special one for local/SYSOP only uploads! >
### ----------------> New in RBatch 1.75 <---------------- ###
RBatch now supports colorized UPCAT.HLP files for users that
have color chosen as their graphics type. The program will look
for the following:
Non-Color Graphics Choice Color Graphics Choice
------------------------- ---------------------
UPCAT.HLP UPCATC.HLP
You will note that the program looks for the filename with a "C"
appended to the filename. If the "C" file does not exist then
the non-color file is used. Also, remember that you can call
RBatch's UPCAT.HLP file whatever you wish, as long as it is specified
in the configuration file.
14. Are you using FMS or .DIR?
Enter: FMS or DIR
15. Default Category or Path/Name of SysOp-only uploads file (.DIR):
This is the category given to uploads:
1. that are saved by the SysOp after a user times out
(falls asleep, too busy getting a beer, etc.) during or
after the upload WITHOUT entering the category.
2. if a user drops carrier during the upload process.
3. where the user does not have a high enough security level
to categorize uploads.
If the SysOp is using the .DIR file system, then this entry will be
the path/name of the file that the SysOp wants the personal (/) uploads
posted to. This file is only for the .DIR file system and not the FMS.
-8-
16. Compression type all files are converted to:
Enter "NONE" if you perform no conversions in your Batch File
If you have batch files (PHASE?.BAT, CARCZIP.BAT, etc.) which convert
all uploaded files to a common format, enter the extension converted
TO here, otherwise, enter "NONE."
17. Save files on User Timed Out or Dropped Carrier Uploads?
Enter: YES or NO
==== See section below on "User Time-Outs and Dropped Carriers" ====
18. Use Fossil Driver?
Enter: YES or NO
RBatch has support for the fossil drivers X00 or BNU.
Enter either "YES" or "NO" on this line in the configuration file.
(We also support 16550AFN UARTS.)
==== If you run with a special type of COM Port setup (non-standard ====
IRQ's, etc.) you will be required to utilize a FOSSIL driver,
or RBatch will not function properly!
19. Size of first FMS/.DIR File Description Line:
Enter: a number from 40 to 46
20. Number of Lines for Extended Descriptions;Use BAMA support?
Enter: # of lines;YES or NO
Place the value of the maximum number of lines you will allow in
your FMS/.DIR's for extended FMS descriptions as the FIRST parameter
on this line. As a second parameter, enter either "YES" or "NO"
--"YES if you use the BAMA WHO mod for posting the name of the
uploader to the FMS, "NO" to disable this feature.
==== (For NO extended descriptions, enter "0" as the FIRST parameter.) ====
21. Use FFS System;Path/Name of Fidx.Def file?
Enter: YES or NO for using FFS System
It is assumed that if the SysOp uses the TAB file of the FFS system,
that the filename is the same as the FIDX.DEF file, except that it
has a "T" in it, (i.e. FIDX.DEF, FIDXT.DEF) and that that TAB file
is located in the same directory (second parameter of this line is
the Path/Name) as its FIDX.DEF file.
-9-
22. Path/Name of file listing Directories to check for duplicate Uploads:
This is a FILE that contains PATHS to file directories
to be checked for duplicate files in ADDITION to the ones that the
FFS already indexes. Here is an example of a listing:
Do not enter each of these paths in the configuration file!!
The filename you specify on the configuration line contains
these paths.
c:\temp\
c:\testing\
d:\other\
==== (One directory per line, and each line must end with a backslash!) ====
If you specify "NO" for using a FFS system in line #22, then this
list of directories is what is used by RBatch to check for duplicate
uploads.
23. Environment Running under (choose one):
Enter: DOS - Running RBBS-PC\RBatch in DOS
DV - Running RBBS-PC\RBatch in DV
NET - Running RBBS-PC\Rbatch in a Network Environment
that REQUIRES running DOS's SHARE.EXE
24. BBS Name to appear on Registered Versions:
Enter: 50 characters Maximum
25. Registration Number:
Enter: 20 Alpha-Numeric Registration Code
(Input all "0"s if unregistered)
26. Process .DIZ/.SDI/.DOZ files?;Work Directory;File with archive commands:
1 2 3
Enter: 1. YES or NO - This tells RBatch to process FILE_ID.DIZ,
DESC.SDI, or .DOZ files.
2. Path to the work directory we will use to decompress
the DIZ, DOZ*, or SDI file into. NOTE: This directory
must actually exist in order to process these files!
RBatch creates, then deletes, NODE# directories under
this specified directory.
3. The THIRD parameter is the filename that contains
a list of archive extensions and their associated
command lines for DEcompressing (unZIPping, unARCing,
etc.) for the decompressors that you wish to support.
-10-
Ex.: ARC.LST (or whatever name you choose) is a text file
like this:
ARJ;C:\RBBS\ARJ E
ZIP;C:\PKZIP\PKUNZIP -O
^ ^
1 2
The FIRST part is the extension to process
The SECOND parameter is the path/command line
to use for that particular extension.
==== NOTE: If a file is uploaded and its extension does not match an
entry in this file, the upload will not be checked for an
embedded description file (FILE_ID.DIZ or DESC.SDI).
* For more information on .DOZ files, see the
WHATISA.DOZ file included in this archive.
27. ### ----------------> New in RBatch 1.75 <---------------- ###
SysOps may now specify the NAME of the batch files that RBatch calls
for upload checking by adding another line (#27) at the BOTTOM of
the configuration file. If NO ADDITIONAL LINE IS ENTERED, the program
defaults to the PHASE?.BAT files. This new parameter allows you to
have separate BAT files for each NODE, for example, or one set of
BAT files to process files locally, and another for actual uploads.
Very useful if processing large numbers of files at a time, and you
want to use different process criteria for local uploads, or "real"
ones. REMEMBER, THAT IF LINE 27 IS MISSING, THE PHASE?.BAT's are
used.
***> One important point to remember is that RBatch looks for the batch
file in the SAME DIRECTORY as the Configuration File.
Here are some examples of LINE #27:
-----------------------------------
YES;C:\RBBS\WORK;C:\RBBS\ARC.LST - Currently the last line in config.
LOCAL.BAT;LOCAL1.BAT;LOCAL2.BAT - New line is entered with the names of
the batch files to use.
In this example LOCAL.BAT is called first, LOCAL1.BAT is called next,
and LOCAL2.BAT is called last.
Here is another example:
------------------------
YES;C:\RBBS\WORK;C:\RBBS\ARC.LST - Currently the last line in config.
LOCAL.BAT;LOCAL1.BAT - New line is entered with the names of
the batch files to use.
In this example LOCAL.BAT is called first, then LOCAL1.BAT, then
PHASE3.BAT is called last.
-11-
And yet another:
---------------
YES;C:\RBBS\WORK;C:\RBBS\ARC.LST - Currently the last line in config.
LOCAL.BAT - New line is entered with the name of
the batch file to use.
In this example LOCAL.BAT is called first, then PHASE2.BAT is called next,
then PHASE3.BAT is called last.
Duh!:
-----
YES;C:\RBBS\WORK;C:\RBBS\ARC.LST - Currently the last line in config.
- No additional line is entered in
this configuration file example.
NOT EVEN A BLANK LINE!!!!
In this example PHASE1.BAT is called first, then PHASE2.BAT is called
next, then PHASE3.BAT is called last.
Note from the examples, that you may specify from one to
three new batch files for RBatch to use. When using more
than one batch filename you MUST separate each name with a
SEMI-COLON!
RBatch will only execute the Batch Files THAT IS CAN FIND.
B-3. Additional notes for the RBatch Configuration file:
--------------------------------------------------
As of v.1.70, the variable [NODE] may be placed into the
configuration file anywhere you use a path/filename option.
When [NODE] is found, RBatch will substitute the node number
from the RBatch Command line in place of [NODE]. This new
feature should allow the SysOp, if they wish, to be able to
use ONE configuration file for all their nodes on the Main
board and one for each Sub-Board.
Here is an example usage:
-------------------------
.
NO;c:\rbbs\node[node]\dorinfo[NODE].def
.
.
c:\rbbs\node[node]\callers[NODE]
.
.
c:\rbbs\xfer\xfer-[NODE].def
.
.
(NOTE: [NODE] is not case sensitive)
-12-
==== Once again I must stress that all the NAMES used in the above
configuration example are optional and SYSOP-configurable.
The only names that RBatch REQUIRES be used are PHASE.BAT,
PHASE2.BAT and PHASE3.BAT, and THEN only IF you do not
specify alternate BAT file names for configuration line #27.
==== Also, make sure that all the lines in the configuration file end with
a carriage return. THERE SHOULD BE NO SPACES AFTER THE LAST ENTRY
ON EACH LINE. IF YOU HAVE SPACES, YOU WILL GET ERRORS AND RBATCH
WILL NOT RUN.
==== A Note about Sub-Boards:
In your RBatch configuration file, you should point to the MAIN
MESSAGE BASE. If your Sub-Board uses aliases the user's REAL NAME
will be in the Main Message base and when RBatch goes to find the
user name in the Users file, it will find a match. You should still
specify the Main Message Base even if you do not use aliases, due to
RBBS reading the Main Message base first upon return from the protocol,
hence time credits have to be written here in order for users to get
credit.
B-4. The RBBS-PC PROTO.DEF Setup:
----------------------------
Equally important to proper operation of RBatch is the structure
of the RBBS PROTO.DEF protocol handling file. This file designates
the way RBBS loads the external protocols, and what information passes
between the two (the system and the protocol) during a file transfer.
Included in this archive are examples of PROTO.DEF setups. Please
refer to these files for assistance in setting up DSZ, HS/Link &
BiModem. Also, if you are not familiar with the structure of the
RBBS PROTO.DEF file, we suggest you familiarize yourself with that
section of the RBBS DOCuments.
Files included here are for EXAMPLE purposes only and all param-
eters and criteria (security levels, paths, etc.) that are unique to
your system need to be changed to match your BBS setup.
Note in the Proto.Def example, that XModem and 1K-Xmodem are shelled
to and do not use RBatch. This was done to show you that all protocols
do not have to use RBatch. If you wish all protocols to use RBatch for
processing, just change the XModem entries to match the ZModem entry
and make a batch file for XModem and 1K-XModem for the downloading and
the uploading side of the Proto.Def.
Remember for RBBS to recognize an entry in the Proto.Def it has to be
able to "find" the batch file or program. If you have your Proto.Def
in a directory called C:\RBBS\XFER and all your batch files and protocols
-13-
are also there, then your entries in the Proto.Def should have paths.
Here is an example:
....."C:\RBBS\XFER\BATCHDN.BAT [PORT#] [BAUD] [PROTO] [NODE]",".....
Note that this example only shows the "download side" of the Proto.Def
entry, but I hope you get the idea.
The only major REQUIREMENT for RBatch is that it requires DOORING to
the protocol. DO NOT SHELL!!! This is an easy modification--requiring
typing one letter in each line of your PROTO.DEF file. (Change the "S"
to a "D.")
B-5. Batch Files used in PROTO.DEF:
-----------------------------
Also included in this archive are examples of the batch files that are
used in our PROTO.DEF examples.
The file BATCH.ZIP contains:
BATCHUP.BAT BATCHUPY.BAT BATCHUPG.BAT
BATCHDN.BAT BATCHDNY.BAT BATCHDNG.BAT
The file HSLNKBAT.ZIP contains the two batch files:
HS1UP.BAT HS1DN.BAT
(These are for use with HS/Link)
The file BIMODEM.ZIP contains the:
- A sample PROTO.DEF setup for Bimodem/RBatch.
- Sample BAT files used in PROTO.DEF (BI1UPA.BAT & BI1DNA.BAT).
- An example of an RBatch/BiModem configuration file.
(Again, note that these are examples and are to be used only as guidelines
and should be modified to match your BBS setup.)
SPECIAL NOTE on BATCHUPx.BAT:
For uploads with the DSZ protocols, these sample batch files first
change to the upload drive & directory and then invoke the DSZ protocol.
I have done it this way to show how SysOps who do not have a registered
version of DSZ can designate an "Upload Directory." With a registered
version of DSZ, you may specify the path on the DSZ command line.
-14-
Check the DSZ documentation (sort of like suicide, huh?) for the proper
command line for registered versions.
B-6. The RBatch COMMAND line:
-----------------------
The RBatch command line syntax is as follows:
RBatch <Path/Config Filename> <Port #> <Proto Letter> <Node #>
The config filename may have a path to it and the
other parameters can be passed from your PROTO.DEF
command lines with:
<Port #> = [PORT#] NOTE: Use [PORT#]-not [PORT]!
<Proto Letter> = [PROTO]
<Node #> = [NODE]
If your proto.def looked like this:
"C:\RBBS\XFER\BATCHDN.BAT [PORT#] [BAUD] [PROTO] [NODE]"
Your RBatch command line would look like this:
RBatch Rbatch.cfg %1 %3 %4
B-7. SysOp Designed Batch Files (Phase1.Bat, Phase2.Bat, Phase3.Bat,
Phase1c.Bat, Phase2c.Bat, Phase3c.Bat,
or whatever name(s) you specify on line
#27 of the configuration file):
--------------------------------------------------------------------
These are the BATCH files (called in numerical order--PHASE1.BAT,
PHASE2.BAT, PHASE3.BAT) that the SysOp creates or customizes for
testing each uploaded file. The ONLY REQUIREMENT we have is that
if your batch file locates an error (corrupted ZIP, virus, unacceptable
date range, etc.), it MUST delete the uploaded file!
Why? It's simple.
If, upon return from the batch file, RBatch finds the uploaded file,
it assumes the file tested OK during the batch file test (remember,
RBatch itself tests nothing but the EXISTENCE of the file), and IF
the file is still there, RBatch proceeds to get a description and
category, then posts it to the FMS/.DIR, CALLERS, and USERS files.
-15-
B-8. PHASE?.BAT passed parameters:
-----------------------------
In the batch file command line, we send five parameters along with
the batch filename:
%1 The first is the path & name of the uploaded file.
%2 The second is the extension of the file (No Period)
%3 The third is the node number.
%4 The fourth is the filename with no period or extension.
%5 The fifth parameter is the path to the upload directory.
(No trailing backslash)
B-9. Calling other testers from PHASE?.BAT:
-------------------------------------
If your system is already set up with an upload tester like ZIPLAB,
RBatch will work right along with it, letting ZIPLAB handle all the
upload testing. Or, you could use the old RBBS standard upload
testers. For example, PHASE1.BAT might read:
@ECHO OFF
CLS
if %2 == ZIP GOTO ZIP
if %2 == ARJ GOTO ARJ
:ZIP
tzip.bat %1 %2 %3 %4 %5
:ARJ
tarj.bat %1 %2 %3 %4 %5
As you see, RBatch lets you use your existing batch files for checking
uploads from RBBS, or you can create some new ones.
B-10. Examples of PHASE?.BAT:
----------------------
Example--PHASE1.BAT:
@echo off
cls
if %2 == ARJ goto :ARJ
if %2 == ZIP goto :ZIP
goto :END
:ZIP
echo "Checking File Integrity" > COM1
pkunzip -t %1 > NUL
if errorlevel 1 goto :DEL
-16-
goto :END
:ARJ
echo "Checking File Integrity" > COM1
arj t %1 > NUL
if errorlevel 1 goto :DEL
goto :END
:DEL
del %1 > NUL
echo The file %4.%2 failed the Integrity > COM1
echo Test and has been deleted from this BBS... > COM1
:END
seterror 0
B-11. Colorized (ANSI/High Ascii) BAT files:
--------------------------------------
If the user has graphics turned on, then RBatch will call the batch
files PHASE1C.BAT, PHASE2C.BAT & PHASE3C.BAT so you can use colorized or
graphic batch files. If the "C" version batch files do not exist,
then the normal ones (without the "C") are used.
Example--PHASE1C.BAT:
@echo off
if %2 == ARJ GOTO :ARJ
if %2 == ZIP GOTO :ZIP
if %2 == GIF GOTO :GIF
GOTO :END
:ZIP
if not exist %1 GOTO :END
echo @[2J > gate1
echo @[1;37m > gate1
echo. > gate1
echo. > gate1
echo IMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM; > gate1
echo : Checking ZIP Integrity of Upload : > gate1
echo HMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM< > gate1
echo. > gate1
echo. > gate1
pkunzip -t %1 > NUL
if errorlevel 1 GOTO :DEL
GOTO :END
:ARJ
if not exist %1 GOTO :END
echo @[1;36m > gate1
echo. > gate1
echo. > gate1
echo IMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM; > gate1
echo : Checking ARJ Integrity of Upload : > gate1
echo HMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM< > gate1
echo. > gate1
-17-
echo. > gate1
arj t %1 > NUL
if errorlevel 1 GOTO :DEL
GOTO :END
:DEL
del %1 > NUL
:GIF
echo @[2J > gate1
echo @[1;33m > gate1
echo. > gate1
echo. > gate1
echo. > gate1
echo. > gate1
echo. > gate1
echo. > gate1
echo. > gate1
echo IMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM; > gate1
echo : **** : > gate1
echo : The Policies of this BBS state that : > gate1
echo : GIF's are UNWANTED FILES! : > gate1
echo : THE UPLOADED .GIF FILE HAS BEEN DELETED!!!! : > gate1
echo : **** : > gate1
echo : You agreed to these Policies when : > gate1
echo : you first logged onto this BBS : > gate1
echo : as a New User : > gate1
echo HMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMM< > gate1
echo @[0m > gate1
del %1 > NUL
:END
seterror 0
This example will show to the user that the batch file is checking file
integrity by echoing out the gate#. The line "echo." is for echoing a
blank line (thanks to Fred Busteed for this command). Note that the
gate# is from using GATEWAY as your replacement for DOS's CTTY command.
If you decide to use GATEWAY, be sure to make the appropriate change
in your RBBS configuration file. You can also use gate%node% if you set
the node in your autoexec.bat or your DV startup bat (SET NODE=1).
----------------------------------------------------------------
There are more examples included in the file called EXAMPLES.BAT
----------------------------------------------------------------
-18-
### ----------------> New in RBatch 1.75 <---------------- ###
B-12. Alternate Batch filenames:
--------------------------
If you wish to use batch files with names other than PHASE?.BAT, then
specify on line #27 of the configuration file, the name(s) of the other
batch files to use. You may, for example, choose a different filename
to call for LOCAL uploads, or for SYSOP FMS postings. (Refer to example
27 in section B-1 for a detailed description of this feature.)
B-13. Flexibility in RBatch file processing:
--------------------------------------
These batch files and their parameters will help RBBS SysOps process
many different types of compressed files. Personally, I prefer the
ZIP format, but in order to allow the flexibility all RBBS SysOps have
learned to love, I feel that you should have the ability to accept
all types of files, convert to whatever format you prefer, and still
be able to check the file for the protection of your system and your
users.
C. MISCELLANEOUS INFORMATION:
C-1. Use of "Recovery" with Protocols & RBatch:
------------------------------------------
Most of the protocols that work with RBatch, support file recovery.
There are two things to consider with recovery, however. One concerns
your BBS and the other concerns how RBatch treats the file. With
recovery, you take the chance of introducing a virus into your system
unless you have proper file checking procedures. With RBatch, file
recovery presents a different kind of problem. If you allow recovery
on your system, and a user uploads a file, and your system already HAS
that file, the protocol will report a good upload in its XFER-?.DEF!
RBatch, being very loyal, and trusting his little buddy, XFER, will
process the file as if it were being uploaded for the first time.
This means that you will get this file posted twice in your FMS or
.DIR, but you will only have one copy of the file. It is up to
the SysOp to decide if he/she wants recovery or not.
C-2. User Time-Outs and Dropped Carriers:
------------------------------------
The program also contains a "time-out" feature that will go into
effect in no keyboard input is received within three minutes. The
timer starts each time a user is prompted for a category code and
file description. When a user reaches a time-out, the uploaded file
RBatch is currently working on is either saved or deleted per the
-19-
configuration setup (Line #17). Subsequent uploads that have not
been processed are also either saved or deleted as per line 17.
(NOTE: Files saved in this manner are posted to the FMS or .DIR
with the default category code for FMS or go in the designated
upload directory for .DIR)
- All files that are uploaded are logged to the CALLERS file,
and are also posted to the FMS/.DIR if the SysOp is saving
files (Line #17 of the configuration file).
- Entries in the CALLERS file will end with a ### if a
time-out has occured
- Uploaded files processed after a timeout, are not
credited to the user, but all downloads are. This
is due to RBBS handling the downloads.
The program also monitors carrier, and a dropped carrier is
treated the same way as a timeout (see above).
C-3. RBatch Error Logging:
---------------------
When RBatch detects an error, it will write to its own error log. This
file which is called RBATERR.LOG, will reside in the current directory
where RBatch is executed from. The format for this file is as follows:
<Error Message> <Node #> <Date> <Time> <File>
Here is an example:
Cannot find XFER-?.DEF 1 01-05-92 22:34:01 c:\rbbs\xfer-1.def
This translates into.......RBatch could not find the XFER-?.DEF file
in the location you specified in your configuration file. This
error occurred on Node 1 on 1/5/92 at 10:34pm.
Also note that the error for not finding the XFER?.DEF will be posted
in the RBATERR.LOG when a user aborts an upload, since on an aborted
upload, the XFER-?.DEF file never gets created, hence never found by
RBatch. One way to get around this is to put in your UPLOAD batch
file that is called from the Proto.Def statements like:
c:\rbbs\dsz port %1 speed %2 rz -m
if not exist c:\uploads\xfer-1.def goto :END
c:\rbbs\rbatch c:\rbbs\rbatch.cfg %1 %3 %4
:END
With this example the batch file checks for the exitance of the
XFER-1.DEF file and if it is there, runs RBatch, otherwise it
just exits the batch file and returns to the BBS.
-20-
### Note also that the %# parameters and the pathnames are only
FOR AN EXAMPLE and should be changed to match your setup.
### DO NOT DO THIS for a Bi-Directional Protocol on the
download side, only on the upload side!!!
C-4. What do the included Merges do?
-------------------------------
NOTE: You do not need to use the merges to be able to run RBatch!
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Included in this archive are two merges inside the filename
MRG0812.ZIP, one for RBBS-PC 17.3C & one for v.17.4. These merges
will allow RBBS-PC to check a stacked list of filenames that a user
enters after the "Upload what file(s)" prompt. Each filename will
then be checked to see if the file already exists, and if there are
any duplicates, a list of filenames will be shown to the user and
the upload process aborted. These merges are in Bled 2.2 format.
A batch file is also included to aid in the bled process.
C-5. Why is RBatch an external program?
----------------------------------
The main reason for designing RBatch as an external interface
instead of relying on internal merges was simple: not all
individuals care to recompile RBBS code (only the REAL hard core!),
and merges for ALL versions of RBBS (12 through 17.4) would have
had to be written. Also, PROPER execution of batch uploading inside
RBBS would require a major rewrite of the code, and considering the
number of versions out there, this alternative is unacceptable.
With an external interface like RBatch, everyone can offer batch
and Bi-Directional transfers now.
C-6. Companion Program for RBatch:
-----------------------------
Tom Hansen of Church Chatters BBS has written a companion program for
use by the users of your BBS to aid them with Batch Uploading, called
TAG160.ZIP (Check for future updates also, with more features and
enhancements!)
This program is designed to simplify the BATCH uploading process for
your users. Your users can tag files for uploading and prepare their
batch uploading sessions in a few simple key strokes. It supports
bidirectional protocols and the popular DSZ protocols and allows for
a user configurable protocol if one of their favorite protocols is not
an available option. This program will assist you in training and
encouraging your users to utilize your BATCH uploading capabilities.
-21-
C-7. Warranty & Disclaimer:
----------------------
THIS PRODUCT IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND,
INCLUDING ANY WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR
PURPOSE. THE ENTIRE RISK AS TO THE RESULTS AND PERFORMANCE OF THE
PROGRAM IS ASSUMED BY YOU. FURTHERMORE, I THE AUTHOR DO NOT WARRANT,
GUARANTEE, OR MAKE ANY REPRESENTATIONS REGARDING THE USE OF OR THE
RESULTS OF THE USE OF THE PROGRAM, OR THAT THE PROGRAM WILL RUN WITHOUT
ERROR, AND YOU RELY ON THE PROGRAM AND RESULTS SOLELY AT YOUR OWN RISK.
I THE AUTHOR CANNOT ACCEPT RESPONSIBILITY FOR SYSTEM DAMAGE, LOSS OF
PROFIT, OR ANY OTHER SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES
RESULTING FROM THE USE OR INABILITY TO USE THIS PRODUCT.
As always, with any new program, you should have backup copies of your
MESSAGES, USERS, FMS or .DIR, and CALLERS files when first installing and
using RBatch, since it uses these in its operation.
This program is ZIPPED with Authenticity Verification. If you do not
see the registration number of "# MMJ131 THE SHORELINE BBS, there is
a possibility that it is not an official version or the BBS you
received it from re-zipped the file and stripped off the -AV.
You can always call my BBS and download the official version.
C-8. Registration:
-------------
This program is being released under the "shareware" concept. This means
that you can try it out to see what it is like for a period of time. If
after a period of 60 days you continue to use it on your BBS, then regis-
tration is required. If you do not wish to register the program, then
you must discontinue use of the program (the Shareware Police are
everywhere, so beware!).
The program is not "Crippled" in any way, and what you get with a
registered version is your BBS name on the opening screen, and the
ending screen telling users that it is unregistered, is removed.
You will also get "Visiting SysOp" access to my BBS which entitles
you to 60 Minutes/day, and unlimited file downloading.
I have chosen not to "cripple" the program because I don't believe in
"crippleware", but with this concept, less people tend to register it.
I hope that when you use the program you find that it is an excellent
addition to your BBS, hopefully then registering it.
-22-
Registration lets me know that the program I worked very hard on is
appreciated. It will also encourage me to write other useful
programs/enhancements for RBBS SysOps in the future.
Once you register RBatch, it is registered for any new version that may
come out in the future.
You can get your registered version one of two ways:
----------------------------------------------------
First, for $20.00, mail in the registration form with all the questions
filled in. You then call my BBS and get your registration number in a
private message to you along with a file in the personal files section.
Second, for $25.00, you can send me the registration form with all the
questions filled in along with the size of the diskette you wish to
receive (5 1/4 or 3 1/2). I will then mail you the latest version of
the program along with your registration number.
C-9. Acknowledgments:
-----------------
I would like to thank a few individuals for their support and ideas
without whom this program would not have been possible.
First of all, to my wife Linda, my son David, and my daughter Linnea
for time and again putting up with me parking myself in front of my
computer for hours on end to work on the program. (Hey David, we
probably would have gotten a lot farther in Super Mario Brothers 3
if I hadn't been working on this program!!! <G>)
Second, to my Beta Testers--Tom Hansen, Walter Ames, David Brodmann,
Gregg Snyder, Gary Slemp (for helping out with the tedious task
of writing this documentation), and Tate Biersack. Their ideas
and testing of the program for any sort of bug possible, made it a far
superior product than it would have ever been.
Third, to all the people who work on RBBS, and make it the best BBS software
available. And last, Borland International Inc., and Data-Comp Information
Systems, for their great software.
-23-
C-10. Support:
--------
If you do encounter any problems with the program, or have suggestions
on improvements, you can call my BBS 24 hrs a day, and leave a message
for me, or leave a message on the RIME Network in the RBBS conference,
or in the RBBS-PC or RBBSSYS conference on the RBBS-NET Network (Another
SysOp friend of mine carries the RBBS-NET and will alert me if there are
messages for me). I will consider the enhancements and of course try to
fix any problems encountered with the program.
Note that I support both Registered and Non-Registered users of the
program. Support is a NUMBER ONE priority for me and my programs,
and I think you will be impressed with the support that I give. You
are welcome to call me voice if you have any problems between 7-10:00pm
weekdays and between 9am-10pm on the weekends.
My BBS name & number are:
Dan Shore
"THE SHORELINE BBS"
Located in Silver Spring, MD
12/24/9600/14.4 HST
301-946-2771
Proud Member of the
- DGS Systems Group (Wonder) -
RBBS-PC Beta Test Site
Proudly Running RBBS-PC
"The Best BBS Software in the World"
Member of the RIME Network
Node ID = SHORLINE
-24-